[Build] Make checkPart4 configuration cache compatible #117250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
breskeby
added
>non-issue
:Delivery/Build
breskeby
force-pushed
the
checkpart4-cc
branch
2 times, most recently
from
66e174b to
7a16c34
Compare
… task execution phase
breskeby
force-pushed
the
checkpart4-cc
branch
from
a1149d6 to
691a8c9
Compare
breskeby
changed the title
|
Pinging @elastic/es-delivery (Team:Delivery) |
breskeby
added
the
auto-merge-without-approval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This makes checkPart4 tasks in general configuration cache compliant.
We do not enable it by default in our pipelines yet. That will eventually be done in separate PRs.
To track any regressions we cover the checkPart4 task in the weekly gradle cache validation build job